Skip to content

libsyntax: Forbid type parameters in field expressions. #18879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

libsyntax: Forbid type parameters in field expressions. #18879

wants to merge 1 commit into from

Conversation

pcwalton
Copy link
Contributor

This breaks code like:

struct Foo {
    x: int,
}

let f: Foo = ...;
... f.x::<int> ...

Change this code to not contain an unused type parameter. For example:

struct Foo {
    x: int,
}

let f: Foo = ...;
... f.x ...

Closes #18680.

[breaking-change]

r? @aturon

@pcwalton
libsyntax: Forbid type parameters in field expressions.
e6e58e4 
This breaks code like:

    struct Foo {
        x: int,
    }

    let f: Foo = ...;
    ... f.x::<int> ...

Change this code to not contain an unused type parameter. For example:

    struct Foo {
        x: int,
    }

    let f: Foo = ...;
    ... f.x ...

Closes rust-lang#18680.

[breaking-change]
bors added a commit that referenced this pull request Nov 13, 2014
@bors
auto merge of #18879 : pcwalton/rust/path-silliness, r=aturon
82f3838 
This breaks code like:

    struct Foo {
        x: int,
    }

    let f: Foo = ...;
    ... f.x::<int> ...

Change this code to not contain an unused type parameter. For example:

    struct Foo {
        x: int,
    }

    let f: Foo = ...;
    ... f.x ...

Closes #18680.

[breaking-change]

r? @aturon
@bors bors closed this Nov 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@aturon aturon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

type parameters on field references are allowed
3 participants
@pcwalton @aturon @bors